Summary

Documents the RocksDB backup & restore feature shipping in 5.2 (companion to HarperFast/harper#1831), in a dedicated Backups reference section:

• Backups / Overview (reference/backups/overview.md) — how the backup system works (incremental managed backups, snapshot download), its limitations (engine support, granularity, single storage root, online-vs-offline restore matrix), and two worked examples: incremental backup/restore with harper create_backup / harper restore_backup, and harper get_backup streaming a tar.gz off-host plus the manual restore procedure (stop Harper, extract into the database directory under storage.path).
• Backups / Operations (reference/backups/operations.md) — all seven operations (create_backup, list_backups, verify_backup, delete_backup, purge_backups, restore_backup, get_backup) with Operations API and CLI examples.
• EngineBadge component (src/components/EngineBadge.tsx, globally registered like VersionBadge) tags storage-engine support per operation: the managed operations are RocksDB-only; get_backup supports both RocksDB and LMDB.
• Operations API (reference/operations-api/operations.md) — Backup & Restore trimmed to the brief index pattern used by Logs/Certificate Management, linking to the new section.
• CLI (reference/cli/commands.md) — the Backup Commands section is removed (content lives in Backups now); the backup operations are listed in the CLI operations table (reference/cli/operations-api-commands.md).
• Configuration (reference/configuration/options.md) — the backupPath storage option (default <rootPath>/backup).
• Release notes (release-notes/v5-lincoln/5.2.md) — Backup & Restore entry, linking to the new section.

Where to look

• The manual-restore example in the Overview instructs extracting the archive into <storage.path>/<database> (default ~/hdb/database/data) — path verified against DATABASES_DIR_NAME in core and rocksdb-js's tar layout (entries unpack directly into a directory that opens as a RocksDB database, including transaction_logs/). Worth a second pair of eyes since a wrong path here damages user data.
• Cross-model review (Codex) surfaced four accuracy issues, all fixed in this branch: the whole-database claim now carves out LMDB get_backup partial exports, the single-root-store restriction is documented as a limitation, the super_user requirement is scoped to server-invoked operations (offline CLI is filesystem-governed), and LMDB manual restore points at storage.path rather than the default-only path. The Gemini review leg failed to run (headless permission denial), so outside-model coverage is Codex-only.
• EngineBadge prop shape is a comma-separated string (engines="RocksDB, LMDB") rendered in the same style as VersionBadge — open to a different design.

Reviewers not assigned — leaving that to you.

Generated by an LLM (Claude Fable 5).

🤖 Generated with Claude Code